gobject-introspection: clean-ups & build docs#87904
gobject-introspection: clean-ups & build docs#87904Ericson2314 merged 5 commits intoNixOS:stagingfrom
Conversation
* format with nixpkgs-fmt * reorder the attributes * use pkg-config instead of the pkgconfig alias * optional → optionals * remove top-level `with lib;`
* remove glibcLocales now that glibc contains C.UTF-8 * remove libintl, that should be in by default or something * update homepage * add gnome team to maintainers * remove the temporary libregress closer its creation
and add comments
|
@GrahamcOfBorg build gobject-introspection |
1 similar comment
|
@GrahamcOfBorg build gobject-introspection |
pkgs/development/libraries/gobject-introspection/absolute_shlib_path.patch
Show resolved
Hide resolved
pkgs/development/libraries/gobject-introspection/absolute_shlib_path.patch
Show resolved
Hide resolved
| buildInputs = [ | ||
| flex | ||
| bison | ||
| python3 |
There was a problem hiding this comment.
cc @FRidh from a cross-compiling perspective we usually used the build-native python interpreter to build python packages, no?
There was a problem hiding this comment.
yes, the build-native one is used in buildPythonPackage.
There was a problem hiding this comment.
maybe they link against the interpreter, that is, use the C API?
There was a problem hiding this comment.
Build scripts need build python and some gobject utils are written in python so they need host python.
| docbook_xml_dtd_43 | ||
| docbook_xml_dtd_43 # FIXME: remove in next release | ||
| docbook_xml_dtd_45 | ||
| python3 |
There was a problem hiding this comment.
Ah. It's in both. That would be fine I suppose.
|
@GrahamcOfBorg build gobject-introspection |
|
|
|
@GrahamcOfBorg eval |
1 similar comment
|
@GrahamcOfBorg eval |
|
I just built x86_64 linux and darwin. |
Motivation for this change
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)